Home › Discussions › Questions & Answers › Custom Trigger Conflict during Installation

Custom Trigger Conflict during Installation

Avatar photoCustomer Questions & Answers 3 replies

The installation log shows ORA-04088: error during execution of trigger ‘APPS.NOTE_1342126_1_AUDIT_TRIG’ because FND_LOBS_S.CURRVAL is not yet defined. Why is this audit trigger interfering with the install?

3 replies

  • Support Enginatics

    This specific trigger, often created during an investigation (per Oracle note 1342126.1), is prematurely referencing the sequence’s current value (`CURRVAL`) before it has been initialized in the current session. This trigger should ideally be removed after the investigation, but if still required, it must be temporarily disabled.

  • How do I safely disable the trigger and then proceed with the installation?

  • Support Enginatics

    You must execute `alter trigger apps.note_1342126_1_audit_trig disable;`, rerun the `install.sh` script, and then re-enable it afterwards using `alter trigger apps.note_1342126_1_audit_trig enable;`.

  • You must be logged in to reply to this post.