Re: Corrupted index that won't fix

[Kirk Brooks via 4D_Tech]

Tim and all,
Good suggestions. I'm working on something else at the moment and actually
try any of these yet. I did run the standard repair on the data as well.
The issues seems to have to do with the composite index made up of the
record id and table name.

As I think about it I decided using table names was a bad idea because they
can be so easily changed and would corrupt exactly that sort of thing. I
changed it to table number. The fact the error log shows the old name might
be clue.

I'll report back once I can get into it again.

On Sun, May 21, 2017 at 1:00 PM, Tim Nevels via 4D_Tech <
4d_tech@lists.4d.com> wrote:

> On May 21, 2017, at 9:00 PM, Kirk Brooks wrote:
>
> > Checking index pages on Cluster Index 167 on DOX_ATTACH._data ,
> > DOX_ATTACH.record_id (tableName_recordId) [200 errors]
> >
> > I'm not sure what else to do besides dropping the index. I'm assuming,
> > perhaps incorrectly, that if the data are good the index should be able
> to
> > write itself correctly.
> >
> > I'm hoping one of you can give me some insight into how to correct this.
> > The server is running 15.3 on Win 7.
>
> I had a situation with a damaged index and trashed the .4dindx file to
> rebuild all indexes. I ran MSC again and the index damage was still there.
> I did an MSC data file repair and that fixed the problem.
>
> I had the same idea as you Kirk that index damage could be fixed with just
> an index rebuild but in this situation it required a data file repair.
>
> Curious what kind of index damage you had. Mine mentioned something about
> "null clusters" if I remember correctly.
>
> Tim
> Sent from my iPad
> **
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: http://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
> **
>



-- 
Kirk Brooks
San Francisco, CA
===

*The only thing necessary for the triumph of evil is for good men to do
nothing.*

*- Edmund Burke*
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: Corrupted index that won't fix

[Tim Nevels via 4D_Tech]

On May 21, 2017, at 9:00 PM, Kirk Brooks wrote:

> Checking index pages on Cluster Index 167 on DOX_ATTACH._data ,
> DOX_ATTACH.record_id (tableName_recordId) [200 errors]
> 
> I'm not sure what else to do besides dropping the index. I'm assuming,
> perhaps incorrectly, that if the data are good the index should be able to
> write itself correctly.
> 
> I'm hoping one of you can give me some insight into how to correct this.
> The server is running 15.3 on Win 7.

I had a situation with a damaged index and trashed the .4dindx file to rebuild 
all indexes. I ran MSC again and the index damage was still there. I did an MSC 
data file repair and that fixed the problem. 

I had the same idea as you Kirk that index damage could be fixed with just an 
index rebuild but in this situation it required a data file repair. 

Curious what kind of index damage you had. Mine mentioned something about "null 
clusters" if I remember correctly. 

Tim
Sent from my iPad
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: Corrupted index that won't fix

[Alan Chan via 4D_Tech]

If you have removed a table or field, then add new table or field, it might 
cause problem if the old data is still there.

Repair it might help. It won't harm if it doesn't.

Alan Chan

4D iNug Technical <4d_tech@lists.4d.com> writes:
>I verified a data file and MSC reported the data were fine but the indexes
>had some errors. No problem, I think, I'll just trash the index files,
>restart and let them rebuild. After doing this twice the indexes are still
>showing as :
>
>Cluster Index 167 on DOX_ATTACH._data , DOX_ATTACH.record_id
>(tableName_recordId) [OK]
>Checking index Cluster Index 167 on DOX_ATTACH._data , DOX_ATTACH.record_id
>(tableName_recordId) [OK]
>Checking index page addresses on Cluster Index 167 on DOX_ATTACH._data ,
>DOX_ATTACH.record_id (tableName_recordId) [OK]
>Checking clusters on Cluster Index 167 on DOX_ATTACH._data ,
>DOX_ATTACH.record_id (tableName_recordId) [OK]
>Checking list of deleted clusters on Cluster Index 167 on DOX_ATTACH._data
>, DOX_ATTACH.record_id (tableName_recordId) [OK]
>Checking index pages on Cluster Index 167 on DOX_ATTACH._data ,
>DOX_ATTACH.record_id (tableName_recordId) [200 errors]
>
>I'm not sure what else to do besides dropping the index. I'm assuming,
>perhaps incorrectly, that if the data are good the index should be able to
>write itself correctly.
>
>I'm hoping one of you can give me some insight into how to correct this.
>The server is running 15.3 on Win 7.
>
>

**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: Corrupted index that won't fix

[Arnaud de Montard via 4D_Tech]

> Le 21 mai 2017 à 04:15, Kirk Brooks via 4D_Tech <4d_tech@lists.4d.com> a 
> écrit :
> 
> I verified a data file and MSC reported the data were fine but the indexes
> had some errors. No problem, I think, I'll just trash the index files,
> restart and let them rebuild. After doing this twice the indexes are still
> showing as :
> 
> Cluster Index 167 on DOX_ATTACH._data , DOX_ATTACH.record_id
> (tableName_recordId) [OK]
> [...]
> Checking index pages on Cluster Index 167 on DOX_ATTACH._data ,
> DOX_ATTACH.record_id (tableName_recordId) [200 errors]

Entering the voodoo zone. 

I'm wondering about the index… What are the types of fields DOX_ATTACH._data, 
DOX_ATTACH.record_id? Could you explain?

Or a problem in the data… I'd try a "touch all" on table [DOX_ATTACH]. Some 
code here:


-- 
Arnaud de Montard




**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Corrupted index that won't fix

[Kirk Brooks via 4D_Tech]

I verified a data file and MSC reported the data were fine but the indexes
had some errors. No problem, I think, I'll just trash the index files,
restart and let them rebuild. After doing this twice the indexes are still
showing as :

Cluster Index 167 on DOX_ATTACH._data , DOX_ATTACH.record_id
(tableName_recordId) [OK]
Checking index Cluster Index 167 on DOX_ATTACH._data , DOX_ATTACH.record_id
(tableName_recordId) [OK]
Checking index page addresses on Cluster Index 167 on DOX_ATTACH._data ,
DOX_ATTACH.record_id (tableName_recordId) [OK]
Checking clusters on Cluster Index 167 on DOX_ATTACH._data ,
DOX_ATTACH.record_id (tableName_recordId) [OK]
Checking list of deleted clusters on Cluster Index 167 on DOX_ATTACH._data
, DOX_ATTACH.record_id (tableName_recordId) [OK]
Checking index pages on Cluster Index 167 on DOX_ATTACH._data ,
DOX_ATTACH.record_id (tableName_recordId) [200 errors]

I'm not sure what else to do besides dropping the index. I'm assuming,
perhaps incorrectly, that if the data are good the index should be able to
write itself correctly.

I'm hoping one of you can give me some insight into how to correct this.
The server is running 15.3 on Win 7.

-- 
Kirk Brooks
San Francisco, CA
===

*The only thing necessary for the triumph of evil is for good men to do
nothing.*

*- Edmund Burke*
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**