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

IDS 9.21.FC4 Solaris 8 Sun E3500 I want to turn off logging for some development work on one of several databases on our production server. This particular database is not a production database, but exists in the production instance on the the production box. (Don't ask. "Historical reasons.") Anyway I tried to use 'ondblog nolog <database_name>' Nada. Seemed to be waiting. So I tried using 'ontape -N <database_name>' and got a 107 error. So, I figured there must be a recalcitrant user or developer out there, and I would find and kill the offending session. But, there are no sessions for the database in question. None. Further, I'm 99.9% certain that none of the rowids corresponding to tblsnum 100002 (from 'onstat -k') correspond to the database in question. In other words, there are no user sessions, and I can't seem to find any evidence of an existing lock for the database in question. Yet, I cannot do either of the following: 1) 'database <database_name> exclusive'; or, 2) 'ontape -N <database_name>'. In both cases, I get a 107 (lock) error. 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? -- David Grove - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - "I think not," said Descartes, and disappeared.

"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' andsyslocks.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.