Problems caused by Oracle triggers when updating different records in the base table

Because you do not want to use the background code, you want to use the Oracle trigger for Operation updates. But because the trigger updates the base table, deadlock occurs. Therefore, you can use global variables on the Internet to solve this problem, however, an error has been reported in my row-level triggers for unknown reasons. The Code is as follows:

Create or replace package pkg_proinfo_update

As G_process in varchar2; G_id in number;
End;

Create or replace trigger proparent_process_prochild
Before update OF process
ON proinfo
FOR EACH ROW
When (old. proclass = 'General Project ')
BEGIN

FXYDATA. V_ROW: =: new. process;
FXYDATA. V_GUID: =: new. guId;

END;

Create or replace trigger pkg_proproc_update
After update on proinfo
Begin
UPDATE proinfo p SET p. parentstate = pkg_proinfo_update.G_process
WHERE p. parentguid = pkg_proinfo_update.G_id;
End;

Recommended reading:

GoldenGate performs two-way Oracle-Oracle replication without using a Data Pump

One-way Oracle-Oracle Replication Using the GoldenGate Data Pump

How to debug Oracle Data Pump (expdp/impdp)

Oracle Database Export data pump (EXPDP) file storage location

Export of Oracle 10g Data Pump Partition Table