The question would be why does odbc own a "lock" on the image database?
Is the a deadlock of some sort?  If a process is waiting for a lock or has
a lock on a resource, an abort will not take place until the process is
finished or what ever the process is waiting for is available.

Try doing the following if this should happen again.

1) use the program UNDEDLOK.prvxl.telesup.  This is on most user hp3000s.
This will tell you if you have users waiting for locks.

2) If you have glance look at the process stack.  If you have a cntl-block
wait or the process is impeded...this is an indication that the process is
waiting for some type of resource.

Rebooting the system should not have caused your database to be corrupted
unless there is something else going on ...For example, are you having disc
problems?

Hope this helps

Cathlene Mc Rae
SR HP Response Center engineer.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *