Database Users

Hello, I am querying DBA_DDL_LOCKS and and I see that some of the lock types are triggers. My question is, what are some of the reasons that could cause a trigger to be locked? Thanks,23jb

It's possible that your trigger is requesting access to a locked table? You can query DBA_BLOCKERS and DBA_DDL_LOCKS to see the blocker and the locks.  You need to move your questions to General Database Discussions 

23jb wrote: Hello, I am querying DBA_DDL_LOCKS and and I see that some of the lock types are triggers. My question is, what are some of the reasons that could cause a trigger to be locked? Thanks,23jbTrigger is just PL/SQL that runs when  certain action is initiated.Locks are Oracle way for managing contention to critical objects.  SELECT Decode(request, 0, 'Holder: ',                        'waiter: ')        ||vl.sid sess,        status,        id1,        id2,        lmode,        request,        vl.TYPE FROM   v$lock vl,        v$session vs WHERE  ( id1, id2, vl.TYPE ) IN (SELECT id1,                                         id2,                                         TYPE                                  FROM   v$lock                                  WHERE  request > 0)        AND vl.sid = vs.sid ORDER  BY id1,           request;    

23jb wrote: Hello, I am querying DBA_DDL_LOCKS and and I see that some of the lock types are triggers. My question is, what are some of the reasons that could cause a trigger to be locked? Thanks,23jbDoing an action that requires the trigger to executed will put a DDL lock on the trigger to prevent it from being dropped/modified while it is being executed. https://docs.oracle.com/database/121/SQLRF/ap_locks002.htm#SQLRF55509 :Automatic Locks in DDL OperationsA data dictionary (DDL) lock protects the definition of a schema object while it is acted upon or referred to by an ongoing DDL operation. For example, when a user creates a procedure, Oracle Database automatically acquires DDL locks for all schema objects referenced in the procedure definition. The DDL locks prevent these objects from being altered or dropped before procedure compilation is complete.Oracle Database acquires a DDL lock automatically on behalf of any DDL transaction requiring it. Users cannot explicitly request DDL locks. Only individual schema objects that are modified or referenced are locked during DDL operations. The whole data dictionary is never locked.DDL operations also acquire DML locks on the schema object to be modified.

It would be useful to post the query and the results so that we're all clear about what you are seeing. While a trigger is executing, a lock needs to be taken out to ensure that no one can do DDL on the trigger.  I don't know whether that is really what you are seeing, though, or whether you really mean that your trigger is acquiring locks on other objects. Justin

I am querying DBA_DDL_LOCKS and and I see that some of the lock types are triggers.Do you understand that we can NOT SEE ANYTHING unless you actually post it? Don't just say you 'see' something. Post it so we can see what you are talking about. You need to SHOW US: 1. WHAT you do2. HOW you do it3. WHAT results you get My question is, what are some of the reasons that could cause a trigger to be locked? My question is why didn't you first read the Oracle docs to see if they answered YOUR question? The subject you provided for this thread is 'triggers ddl locks'. A simple web search using EXACTLY those same words gives this as the very FIRST result:https://docs.oracle.com/cloud/latest/db112/SQLRF/ap_locks002.htm#SQLRF55509  If you add 'oracle 12' to the search term the very first result is the same doc Andrew posted that you marked as correct. Answer to questions about basic functionality is NOT rocket science. You could have found that same doc/answer yourself using EXACTLY the same words you used for the subject of the thread. The MOST IMPORTANT skill you can have, IMHO, is how to find info for yourself quickly and easily. It doesn't get any easier than what I showed you above. Yet you failed to do that. Please try harder next time.