This is a discussion on RE: set lock_trace and capturing the output within the Ingres forums, part of the Database Server Software category; --> PS I should have said "Don't think _lockstat_ will help." -----Original Message----- From: Crisp Bruce To: 'info-ingres@ams.org' Cc: Crisp ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| PS I should have said "Don't think _lockstat_ will help." -----Original Message----- From: Crisp Bruce To: 'info-ingres@ams.org' Cc: Crisp Bruce Sent: 9/16/03 11:26 PM Subject: set lock_trace and capturing the output (Ingres 2.0 under Tru64 Unix) Hello all, Could someone let me know how I can get the output from lock_trace written to a file? We are doing some testing of a locking problem in about 12 hours from now and would like to be able to capture the locking info. for all the testers in a single file. I see (re queries) II_EMBED_SET = "printqry" goes to a file (iiprtqry.log) but I cannot find anything similar for locking. Or maybe there is some other way to get the locking info? Don't think logstat will help and using ipm has not helped much. Thanks very much for your assistance. Bruce Crisp Library and Archives of Canada |