Xref: alice comp.databases.oracle.server:83122
Path: alice!news-feed.fnsi.net!netnews.com!newsfeed.direct.ca!novia!nntp3.cerf.net!nntp2.cerf.net!news.cerf.net!not-for-mail
From: Ted Persky <TPersky@sempra.com>
Newsgroups: comp.databases.oracle.server
Subject: How to Lock an Index
Date: Wed, 02 Feb 2000 13:27:00 -0800
Organization: Sempra Energy
Lines: 22
Message-ID: <3898A124.4A4C992B@sempra.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: news.cerf.net 949526769 13702 159.76.52.177 (2 Feb 2000 21:26:09 GMT)
X-Complaints-To: abuse@cerf.net
NNTP-Posting-Date: 2 Feb 2000 21:26:09 GMT
Cc: TPersky@sempra.com, milin@eng.sun.com
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en

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