Re: Failed Index Creation Recovery

"Don Seiler" <don_at_seiler.us> wrote in message news:94e86aed.0306171201.5e69d3ac_at_posting.google.com...
> Two weeks ago I was building an EXTREMELY large index. Well
> unfortunately it got in the way of business-critical applications with
> it's table locking and I was ordered to kill the index creation. It
> had been running for 6 days.
>
> So afterwards the SMON and DBWR process kicked in. I read that this is
> normal cleanup. However they have been running at a high clip for over
> 8 days now. Is there any way to tell how far along a recovery is?
>
> We are running Oracle 7.3.4.5 on HP-UX.
>
> PS - For future reference, how does one calculate the optimal INITIAL
> and NEXT extent parameters for the CREATE INDEX statement?

At least you could have created the index using the nologging attribute. There would have been no archive logs during creation and no archivelogs during rollback.
You would guess the progression of the rollback can be monitored using v$rollstat.

The number of extents in a segment is irrelevant, so there are no 'rules' to calculate the optimal initial and next.
But above all, you should either get rid of the prehistoric version of Oracle, or quit your job and, like the wizard Catweazle, travel to the current milennium with a current version of Oracle

-- 
Sybrand Bakker
Senior Oracle DBA

to reply remove '-verwijderdit' from my e-mail address