PL/SQL Trying to update a table through trigger on the same table

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • amitpatel66
    Recognized Expert Top Contributor
    • Mar 2007
    • 2358

    #16
    Originally posted by DreamersDelight
    I have allready tried this, I think, check out my code paste in the above post. It still gives me the self-deadlock error.

    Thanks again for the fast replies and helping me out on the issue.
    Does your trigger not mutating?

    Comment

    • DreamersDelight
      New Member
      • Feb 2008
      • 17

      #17
      The error I get is I'm not shure what you mean by that.

      Comment

      • amitpatel66
        Recognized Expert Top Contributor
        • Mar 2007
        • 2358

        #18
        Originally posted by DreamersDelight
        The error I get is I'm not shure what you mean by that.
        Could you please check the following and post back the results:

        [code=oracle]

        select object_name,sta tus from all_objects where UPPER(object_na me) IN ('your triggername in CAPS','your procedure name in caps','your table name in caps','any other object that you make use of in your coe in caps');

        [/code]

        Comment

        • DreamersDelight
          New Member
          • Feb 2008
          • 17

          #19
          Everything returns valid.

          Comment

          • amitpatel66
            Recognized Expert Top Contributor
            • Mar 2007
            • 2358

            #20
            Originally posted by DreamersDelight
            Everything returns valid.
            Try one thing, just comment out the procedure call and then fire the trigger. Lets see if this is because a procedure is performing a DML that is called from a trigger.

            Comment

            • DreamersDelight
              New Member
              • Feb 2008
              • 17

              #21
              Originally posted by amitpatel66
              Try one thing, just comment out the procedure call and then fire the trigger. Lets see if this is because a procedure is performing a DML that is called from a trigger.
              Ok, I did what you asked and commented out the update, the trigger fired fine, and the temptable was created succesfully.

              Comment

              • amitpatel66
                Recognized Expert Top Contributor
                • Mar 2007
                • 2358

                #22
                Originally posted by DreamersDelight
                Ok, I did what you asked and commented out the update, the trigger fired fine, and the temptable was created succesfully.
                So the call to a procedure from a trigger is causing a problem here right. Try this: Make the procedure an Autonomous by adding PRAGMA derivatives, and then try calling a procedure from a trigger and check if it works?

                Comment

                • DreamersDelight
                  New Member
                  • Feb 2008
                  • 17

                  #23
                  Originally posted by amitpatel66
                  So the call to a procedure from a trigger is causing a problem here right. Try this: Make the procedure an Autonomous by adding PRAGMA derivatives, and then try calling a procedure from a trigger and check if it works?
                  No, I don't think that's the problem. I can call procedures fine, even when I put the update statement in a procedure, (currently located in the trigger itself) it will still deadlock.

                  Comment

                  Working...