Re: No user sessions, yet still receive 107 (lock) error

Hi, I'd like to tell you one more idea: Run the commands - in unix: onstat -g sql | head -5 ; onstat -g sql | grep -i <dbname>It shows you the sessions in that database, then, you can see what the sessions does, with: onstat -g sql <session> onstat -u | grep <session> If you want: onmode -z <session> Regards. RFo "rkusenet" <rkusenet@sympatico.ca> wrote in message news:<c616kj$6pjtq$1@ID-75254.news.uni-berlin.de>... > "David E. Grove" <david_grove@correct.state.ak.us> wrote > > > I called tech support and they told me there were phantom locks and I needed > > to bounce the server to clear them. > > > > Is there really no way to fix the problem without bouncing the server? > > Try running this query in sysmaster > > select syslocks.owner > from syslocks, > sysdbspartn,outer syssessions > where syslocks.tabname = 'sysdatabases' and> syslocks.owner = syssessions.sid and > syslocks.rowidlk = sysdbspartn.rowid and > sysdbspartn.name = 'your database name' > > This will tell you those sessions which are not connected directly to > the database in question, but indirectly thru views, synonymns etc. > > if you find some sessions, onmode -z them and hopefully that should > solve your problem. > > good luck.