Should have also mentioned there are a variety of bugs that can cause this behavior. To see the full list of potential bugs for your version of the DB, check out the note: WAITEVENT: "cursor: pin S wait on X" Reference Note [ID 1298015.1] The note also goes through deciphering the p1,p2,p3 to figure out the cause (both the session/statement) creating the problem. The note says: There are 3 main scenarios that cause this event to show up system-wide: ... Job ________________________________ -- //www.freelists.org/webpage/oracle-l