How rebuild index for an empty table?

Kopperton

Member
Hi all,

in 9.1D database sco unixware.
"Index reconstruction utility was aborted. Rerun it to completion"

I found some promissing solution where people succeded where they suggest to rebuild any index of an empty table in empty area

how can I get that and what are the commands I must use? please help me.

thanks all.
 

TomBascom

Curmudgeon
I'm not entirely sure what you're trying to accomplish but it sounds like you might be wanting what is sometimes called a mock index rebuild. It clears certain flags in the database and eliminates the associated error messages but it does nothing to repair the condition behind the message. In other words -- if the message is warning you that the db is corrupt or damaged or whatever it still will be even after faking it out.

To run a mock index rebuild run an index rebuild and select the "some" indexes option. It will prompt you for specific indexes to rebuild. You make it a mock rebuild by immediately terminating the list by entering "!". (Thus there are no indexes to rebuild.) The utility then clears the flags and is done.

Like I said -- this only clears the flags and eliminates the messages. It doesn't fix anything. It may give you a false sense of security.
 

Kopperton

Member
thank you Tom
I am trying to decipher what these guys are saying to remove Reindex error flag, then we can dump&load

thank you again

---------------
"Index reconstruction utility was aborted. Rerun it to completion. (651)
---
Rebuild at least one (any) index e.g. in the table that does not the records at all.
Rebuild any index of any empty table.
I meant: Preferably for table in empty area.
--------
George,
Thanks for the suggestion. I was able to find an index on an empty file to
rebuild. Allowing me in to add the additional extents to the one are that
was hitting the 2gig limit. Now, I'm trying to rebuild the indexes on the
table that crashed during the binary load. Time will tell.
At least now, I know how to get around an index rebuild crash...w/o
restoring.
Thanks again.
----------------
Stephanie,
> At least now, I know how to get around an index rebuild crash...w/o
> restoring.
An alternative solution:
Truncate bi, run proutil -C dbrpr and dump master block.
A byte at offset 22 (V8) or 32 (V9) is a tainted flag (mb_tainted).
Value 32 means that db requires an index rebuild.
Change it to 0 and load the dump back.
-----------------------------
------------------------------
 

Kopperton

Member
PROGRESS Version 9.1D09 as of Fri Apr 14 22:22:25 EDT 2006
Index reconstruction resumes. (2747)
Previous index rebuild was interrupted. This is a new try.
(2748)
Can't find selected index list file .xb; assuming ALL. (2786)
Is this correct? (y/n)

Tom how can I avoid this in mock index build?
 

Kopperton

Member
how can I rebuild index area by area, I want to avoid are 19 for example.
we are running sx.e and progress is 9.1D09
 

Kopperton

Member
how to run this code and spot an empty area?

Code:
/* This code will display all Tables sorted by Area */
 
for each _StorageObject no-lock where _StorageObject._Object-type = 1
    and _StorageObject._Area-number > 6                                       /* to hide system tables */
  by _StorageObject._Area-number:
  
  find _Area where _Area._Area-number = _StorageObject._Area-number  no-lock no-error.
  find _File where _File._File-number = _StorageObject._Object-number    no-lock no-error.
  
  display
    _StorageObject._Area-number format ">>9" column-label "Area"
    _Area._Area-name format "x(30)" column-label "Name"
    _File._File-nam when available _File  column-label "Table".
end.
 
/* This code will display all Indexes sorted by Area */
 
for each _StorageObject no-lock where _StorageObject._Object-type = 2
    and _StorageObject._Area-number > 6 /* to hide system tables */
  by _StorageObject._Area-number:
 
  find _Area where _Area._Area-number = _StorageObject._Area-number    no-lock no-error.
  find _Index where _Index._Idx-num = _StorageObject._Object-number      no-lock no-error.
  if available _Index then find _File of _Index no-lock no-error.
 
  display 
  _StorageObject._Area-number format ">>9" column-label "Area"
  _Area._Area-name format "x(20)" column-label "Name"
  _Index._Index-name format "x(30)" when available _Index
  _File._File-name format "x(20)" column-label "Table of Index" when available _File.
 
end.
 


</SPAN>geovisit();[IMG]http://visit.geocities.com/visit.gif?&r=http%3A//www.geocities.com/ResearchTriangle/3737/progress.html&b=Microsoft%20Internet%20Explorer%204.0%20%28compatible%3B%20MSIE%206.0%3B%20Windows%20NT%205.1%3B%20SV1%3B%20.NET%20CLR%201.1.4322%29&s=1024x768&o=Win32&c=16&j=true&v=1.2[/IMG] [IMG]http://visit.geocities.yahoo.com/visit.gif?us1173051857[/IMG][IMG]http://geo.yahoo.com/serv?s=76001544&t=1173051857&f=us-w76[/IMG]
 

TomBascom

Curmudgeon
PROGRESS Version 9.1D09 as of Fri Apr 14 22:22:25 EDT 2006
Index reconstruction resumes. (2747)
Previous index rebuild was interrupted. This is a new try.
(2748)
Can't find selected index list file .xb; assuming ALL. (2786)
Is this correct? (y/n)

Tom how can I avoid this in mock index build?

A mock index rebuild is a different beast from an aborted index rebuild. I would finish the index rebuild. Presumably it was started for a good reason.
 

TomBascom

Curmudgeon
I think that it might be a good idea to step back a bit here and talk about the bigger picture.

1) You are apparently wanting to dump & load a 9.1d SX.e database?

2) As preparation for that you were doing an index rebuild?

3) The index rebuild failed for some reason?

4) What was the reason for the initial failure of the index rebuild?
 

Kopperton

Member
Hi Tom thank you for your questioins.
1) You are apparently wanting to dump & load a 9.1d SX.e database?
yes!

2) As preparation for that you were doing an index rebuild?
yes! we started with index rebuild not wwith dump&load

3) The index rebuild failed for some reason?
as I recall it encountered errors is bad blocks and memory violation. I was told database being crashed was due to hardware problems which has been fixed. it is marked critical in dell website the firmare for raid controller meaning all our backups are also corrupt.

4) What was the reason for the initial failure of the index rebuild?
same as before bad blocks encountered and violation of memory errors
 

Kopperton

Member
long story short I want to remove "Index reconstruction utility was aborted. Rerun it to completion" message and start dump & load
 

TomBascom

Curmudgeon
There is no need, and almost certainly little if any benefit, to rebuild indexes prior to dump & load. But since you started it you should probably finish it.
 
Top