identifying locks and long locks

Hi, One of our legacy application is being turned logging. We are just converting the database from an unlogged to an unbuffered log. There is no change in application. Right now we are testing whether our application is logging compliant, as it exists now. We sometimes get error -245. I want to identify which session is creating. Is there a sysmaster query for this. specifically I want to write a script to alert me when there is a lock for more than 1 minute. This way I can prove to developers/testers that error -245 is due to someone locking the row and not bothering to release it. thanks. ravi