The article explains how to resolve issue pertaining to APPLY crash with TFO(Trigger Fire Once) Parameter set in the replication
Apply Crashes with TFO issue
Applicable Error Code
FATAL-1651: Set trigger firing failed
Replicate Versions and Oracle Database version 188.8.131.52 and 184.108.40.206
Post database upgrade from version 220.127.116.11 to version 18.104.22.168 APPLY process crash with "FATAL-1651: Set trigger firing failed. Note that _APPLY_TFO_11202 requires Oracle Database 22.214.171.124."
Value of parameter APPLY._APPLY_TFO_11202 is set to YES. Changing the parameter value to NO and restarting APPLY process resolved the Issue. i.e: APPLY._APPLY_TFO_11202 = NO
Possible values of the parameter "_APPLY_TFO_11202" are yes|no|auto . It can be set to AUTO meaning by default Dbvisit Replicate will try to enable it and if not possible then we create a warning.
TFO stands of Trigger fire once - they control whether we try to enable the
fire-once (by default, we do). It's an attribute of trigger you have to set
after it's created (it's not part of the DDL). And fire-once=YES is actually
the default setting for a new trigger.