|
|
FAQ Answerpage
QUESTION:
"The Objectivity tool oocleanup fails to release locks. What do I do next?"
ANSWER:
The use of oocleanup is the only official Objectivity tool that allows you to release locks. To release both update locks and read locks, do the following:
- Check to see that your OO_FD_BOOT is correctly set.
- To view all locks, type the command
oocleanup
- On all hosts that locks exists, type the command
oocleanup -local
- Re-type the command
oocleanup
If locks still appears, make sure the corresponding process is not running and then re-type the command
oocleanup -local
- Sometimes, it may be necessary to type the command
oocleanup -deadowner -transaction {TYPE YOUR TRANSACTION NUMBER HERE}
- If your application generates the error
Cannot grant requested lock; conflict with an existing lock
you might have read locks that are not detected by oocleanup or oolockmon
- Note that sometimes the command oocleanup will generate the error
Recovery already in progress.
- This occurs if one killed oocleanup by using the command
Ctrl-C
and then re-typing the command
oocleanup
- If you receive this error,you need to stop all instances of oocleanup by typing the command
oocleanup -resetlock -transaction {TYPE YOUR TRANSACTION NUMBER HERE}
- If these steps do not work, you might still have read locks that are not detected by oocleanup. In this case, send email to a database group member with your userID and boot file location and they will release the locks for you.
For more related information on databases, see Babar Databases Homepage.
(Last updated 7/11/98)
[SLAC Homepage] [Search] [FAQ Homepage]
If you have a FAQ (with or WITHOUT an answer), use our prototype submission form.
If you have comments or suggestions, email me at sison@slac.stanford.edu
|
|
