Xref: alice comp.databases.oracle.server:83125 Path: alice!news-feed.fnsi.net!newsfeed.icl.net!dispose.news.demon.net!demon!bullseye.news.demon.net!demon!news.demon.nl!demon!sybrandb.demon.nl!not-for-mail From: "Sybrand Bakker" Newsgroups: comp.databases.oracle.server Subject: Re: How to Lock an Index Date: Wed, 2 Feb 2000 22:36:45 +0100 Message-ID: <949527533.8259.0.pluto.d4ee154e@news.demon.nl> References: <3898A124.4A4C992B@sempra.com> Reply-To: "Sybrand Bakker" X-Trace: news.demon.nl 949527533 pluto:8259 NO-IDENT sybrandb.demon.nl:212.238.21.78 X-Complaints-To: abuse@nl.demon.net X-Newsreader: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Lines: 34 You can't lock an index. There is at least one process using the table and as the table is in use it is locked. So the solution would be by means of v$access kill all processes using this table. Hth, -- Sybrand Bakker, Oracle DBA Ted Persky wrote in message news:3898A124.4A4C992B@sempra.com... > Hi gurus: > > Can anyone shed some light on this problem? > > This morning an index was getting close to its MAXEXTENTS value. When I > tried to do an "alter index" to increase MAXEXTENTS by ten, it returned > an ORA-00054 error, that the index was busy and that I had issued the > command with NOWAIT. I couldn't find a "WAIT" option to the "alter > index" command. > > Since I didn't see a "lock index" command, I manually locked its > associated table in exclusive mode. Still, I got the ORA-00054 error. > What process could be accessing the index if I've got the table in an > exclusive lock? What is the best way to lock the index, so that I can > alter the MAXEXTENTS? > > Sincerely, > > Ted Persky > TPersky@sempra.com > >