ORA-04052: ORA-00604:ORA-03106: dblink放在存储过程里执行报错
(2016-03-17 12:05:57)分类: oracle |
存储过程修改:
SELECTzqkh_id into V_ZQKHID FROM T_ZQKH_ACCOUNT_COMPARE_VIEW WHERE crm_id=V_ACCOUNTID;
其它参考:
Compilation errors for PROCEDURE LYJK.SP_RPT_INCOME_DTWO
Error: PL/SQL: ORA-04052: error occurred when looking up remote
object ADMIN.TAR_BOSS_INCOME@BDLY
Line: 15
Text: select 1 DataType, '1月' monthname, sum(ic.JANINCOME)
curmonthvalue , sum(il.JANINCOME) lastmonthvalue from
tar_boss_income ic
Error: PL/SQL: SQL Statement ignored
Line: 15
Text: select 1 DataType, '1月' monthname, sum(ic.JANINCOME)
curmonthvalue , sum(il.JANINCOME) lastmonthvalue from
tar_boss_income ic
解决办法:
create
(
) Authid Current_User
as
BEGIN
ORA-00604 ORA-04052 ORA-03106 ORA-02063 With Any PLSQL Call Via Database Link To Remote Machine With Different OS Platform [ID 559452.1] | |||||
|
|||||
|
修改时间 |
|
In this Document
Applies to:
Oracle Server - Enterprise Edition - Version: 9.2.0.8 and laterInformation in this document applies to any platform.
***Checked for currency on 06-June-2011***
Symptoms
The following errors may occur when running PLSQL code which executes a SQL statement referencing a database on a remote machine.
PL/SQL: ORA-04052: error
occurred when looking up remote object
Changes
This issue occurs only when connecting two databases on two
different machines with different
for example : Windows <=> AIX , or Linux <=> SPARC
To detect the endian of your platform, you can use the following query:select * from
v$transportable_platform;
Cause
bug 5671074
The above is the DDR description of the bug, but it affects
any
Example:
Windows == > little endian.
AIX == > big endian.
This bug only applies to 9.2.0.8 has been solved on 10g and later databases.
Solution
-- To implement the solution, please execute the following steps::1. Login to Metalink.
2. Find and download the patch
https://updates.oracle.com/download/5671074.html
3. Review the attached readme file for the patch installation notes.
4. Apply the patch.
5. Verify the issue after applying the patch.
Note: please choose the correct platform when downloading the patch. Normally you need to apply it
only on the side in where you have the PLSQL issue, but in some cases you may need to apply it on
both sides.
Still have questions ?