Home Discussions Questions & Answers Disabling Trigger Conflict ORA-04088 During Installation

Disabling Trigger Conflict ORA-04088 During Installation

Avatar photoCustomer January 25, 2023 at 8:39 pm

The installation is failing with ORA-04088 on a custom trigger (like NOTE_1342126_1_AUDIT_TRIG) because it reports FND_LOBS_S.CURRVAL is not yet defined in this session.

Viewing 4 reply threads
  • Author
    Replies
    • Support January 27, 2023 at 7:46 am  

      This trigger conflict happens because a custom audit trigger is trying to use a sequence’s CURRVAL before that sequence has been accessed (or initialized with NEXTVAL) in the session.

    • Avatar photoCustomer January 28, 2023 at 9:50 pm  

      This trigger was created by an older investigation. It seems to be interfering with your install script’s flow. How do I proceed?

    • Support January 29, 2023 at 1:09 pm  

      The solution is to temporarily disable the problematic custom trigger. For example: alter trigger apps.note_1342126_1_audit_trig disable;.

    • Avatar photoCustomer January 29, 2023 at 5:56 pm  

      Once disabled, I re-run install.sh?

    • Support January 30, 2023 at 12:21 am  

      Yes, re-run the Blitz Report installation script. After the installation is successful, if the trigger is still needed, you can enable it again using alter trigger apps.note_1342126_1_audit_trig enable;.

Viewing 4 reply threads
  • You must be logged in to reply to this post.

Login with: