You are spot on. Any DDL on the table invalidates the trigger, and a trigger needs to get a lock on the table definition in the library cache while creating. You can find which object it is waiting on by joining P1RAW column to KGLHDADR column in X$KGLOB table. Regards Naveen -----Original Message----- From: Kommareddy, Srinivas (MED, Wissen Infotech) [mailto:Srinivas.Kommareddy@xxxxxxxxxx] Sent: Monday, March 08, 2004 7:18 PM To: oracle-l@xxxxxxxxxxxxx Subject: waiting on library cache locks Hi all, DB:9i Solaris 2.8 When I tried to enable a trigger , its hung for long time. I checked the sessions for any waits. I see that the session is waiting on library cache locks. i further checked and found that the trigger was dependent on a table which is being analyzed that time. Can someone thorugh some light on this. Is the above case true or Is there any other reson for the LC lock ? Tx and Regards, Srinivas