It seemed to be a problem with the address table. I had to end task while indexing during an R5 upgrade of one of our mirrors due to the cache memory release issue in current versions, and address table errors during journal file integrations appeared shortly after bringing the mirror back online in R5.
I restored that data file back to the 17.1 version and verified it and it came back with a completely clean bill of health. I'll try the R5 reindex once again after I figure out how to get it to complete without locking up when the cache memory (~ 400GB) is full. I'm thinking I'll set the cache very high (higher than physical memory) and let Windows handle the memory overflow, so 4D never has to release cache memory. Or buy more RAM. Jeff P.S. - I think issues in the .4DIndy are always indicated by a reference to the table "Resources". > On Aug 8, 2019, at 8:19 PM, Spencer Hinsdale <[email protected]> wrote: > > no but i feel like _you_ posted a while back that is the indy index of > structure ;) > > https://kb.4d.com/assetid=76692 > > Spencer > > > On Aug 8, 2019, at 4:58 PM, Jeffrey Kain via 4D_Tech <[email protected]> > wrote: > >> I ran a verify of our data file, and records were fine, indexes were fine, >> but at the end of the log was an error: >> >> Error: Overlapping Objects in data segment # 65 : Address overlaps(31;140) >> >> >> Does anyone know what this means? ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
