Thank you Colin. Good idea - that worked. And thanks for the info on guide_ndx.
Have a nice day, Amy -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Colin Alfke Sent: Monday, July 13, 2009 1:03 PM To: [email protected] Subject: Re: [U2] UniData 6.1 index corruption Not sure if this was available in 6.1 but here is the help for GUIDE_NDX. Generally, if I have an error in an index and decide to delete it I will delete ALL which also deletes the X_ at the OS level and then completely rebuild it. guide_ndx Syntax guide_ndx{-x |-X}{1|2 |3},{index_names, ... | ALL} [-t template |-T template] filename Description As with other UniData file types, an index file could become corrupt due to hardware failures, the interruption of a write to the index file, or an incomplete write. The guide_ndx utility checks for physical and logical corruption of an index file. If an index file is corrupt, UniData displays a run time error when a UniData process tries to access the index. If the index file is associated with a recoverable file, a message is written to the sm.log. The guide_ndx command creates two files, the GUIDE_XERROR.LIS and the GUIDE_STATS.LIS. GUIDE_ERROR.LIS lists any corruption found in the index file, and GUIDE_STATS.LIS list statistics about the index. If you have a corrupt index, you must rebuild it using the CREATE.INDEX and BUILD.INDEX commands. For more information and creating and building indexes, see Using UniData. Note: We recommend deleting the index with the DELETE.INDEX ALL command. Using the ALL option deletes all alternate key indexes and the index file itself. Parameters The following table describes each parameter of the syntax. Parameter Description -x{1 | 2 | 3} Determines the type of checking guide_ndx performs. * 1 - Performs physical checking * 2 - Performs logical checking * 3 - Performs physical and logical checking index_names The index names you want guide_ndx to check. Separate each index name with a comma, or enter ALL to check all indexes for the file. -t template The template to use for output files. The default is GUIDE. filename The name of the data file containing the index. hth Colin Alfke Calgary, Canada > From: amy_cook > > I'm in the process of rebuilding indexes on our new server (changed > platforms, ran convidx, but rebuilding just to be sure). > > During a BUILD.INDEX FILENAME ALL on one of the files, I kept on getting > disconnected from my telnet session. So I started building the indexes > individually. I isolated the problem one, and then attempted to delete > the index. Got confirmation on screen 'CUST.LAST' deleted, but then it > disconnected my session. Went back in and index still there. > > Trying to gather more information, I listed the file using the index > that's causing problems and get: > > Index: invalid 'next' (2441216) of node 4648960. > > Searching index failed 1 > > > I'm having trouble finding my UD documentation - is there a file utility > specific to indexes? > > TIA, > Amy _________________________________________________________________ Send and receive email from all of your webmail accounts. http://go.microsoft.com/?linkid=9671356 _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
