Re: [U2] [UD] disconnected index
Thanks to everyone who responded to my post. I will DELETE.INDEX ALL and recreate and rebuild them. It must have been related to something we did at the OS level, though I am not exactly sure what that was. Thanks, Josh [EMAIL PROTECTED] wrote: Josh Marcus wrote: Has anyone ever seen a UniData file have its index become disconnected from the data file? I have a file that used to have indexes. I can verify that because I have a LIST.INDEX printout from a few months ago showing them. However, they are no longer in place. When I run LIST.INDEX against the file, it reports there are none. I checked at the Unix level and there was still an index file (X_TX.ARCHV) next to the data file. Not knowing what else to do, I tried to add one of the indexes back to the file. I got this: CREATE.INDEX TX.ARCHV TXA.CAMPAIGN TXA.CAMPAIGN: can not create multiple indices on same location After that, the index showed up in LIST.INDEX. Furthermore, LIST.INDEX tells me the index is built, and selections on the file behave like there are built indexes in place. Anyone have any ideas as to what's going on here? Should I be concerned? The file in question is a dynamic file, if that is of any relevance. System info: UniData 6.0.11 on Tru64 Unix 5.1a. The index for a dynamic UniData file is not stored as X_file. Instead, the index is stored in idx00n partitions inside the directory that holds the primary and overflow partitions. Is it possible that someone converted this file to dynamic recently and the index conversion part of the process didn't go through properly - maybe because of permissions? I've seen scenarios where over zealous system administrators imposed a 0111 umask which meant you could create a new directory for a dynamic file, but couldn't subsequently do much with it because you couldn't list its contents! Anyhow, the X_TX.ARCHV is certainly not related to any indexes on TX.ARCHV if TX.ARCHV is really a dynamic file, in which case TX.ARCHV will be a directory at the OS level. You CAN disconnect an index from a file but leave the OS index files in place, but you either have to have some file corruption, or someone playing cleverly (or stupidly) with fileview. I'd strongly recommend you check the VOC pointer for TX.ARCHV and make sure that the one you are looking at at the OS level is the same one being accessed when you are inside UniData. I'd then check if it really is a dynamic file, and if so, then simply rename your X_TX.ARCHV as something which will remind you to delete it after a day or so. Then run guide against the file to check for any corruption, fix that up with fixfile, and then re-address the indices question. If LIST.INDEX shows you that there really is an index, run guide_ndx against it and consider doing as Colin suggests and DELETE.INDEXing everything before CREATE.INDEXing them again. Cheers, Ken --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UD] disconnected index
Permissions, possibly? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Josh Marcus Sent: Monday, March 14, 2005 9:26 AM To: u2-users@listserver.u2ug.org Subject: [U2] [UD] disconnected index Has anyone ever seen a UniData file have its index become disconnected from the data file? I have a file that used to have indexes. I can verify that because I have a LIST.INDEX printout from a few months ago showing them. However, they are no longer in place. When I run LIST.INDEX against the file, it reports there are none. I checked at the Unix level and there was still an index file (X_TX.ARCHV) next to the data file. Not knowing what else to do, I tried to add one of the indexes back to the file. I got this: CREATE.INDEX TX.ARCHV TXA.CAMPAIGN TXA.CAMPAIGN: can not create multiple indices on same location After that, the index showed up in LIST.INDEX. Furthermore, LIST.INDEX tells me the index is built, and selections on the file behave like there are built indexes in place. Anyone have any ideas as to what's going on here? Should I be concerned? The file in question is a dynamic file, if that is of any relevance. System info: UniData 6.0.11 on Tru64 Unix 5.1a. Thanks, Josh Marcus University Relations, Information Systems University of California, Berkeley --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UD] disconnected index
I've only seen this when moving around files at the OS level. I certainly wouldn't trust this index and would delete and rebuild it. Colin Alfke Calgary, AB -Original Message- From: Josh Marcus Has anyone ever seen a UniData file have its index become disconnected from the data file? I have a file that used to have indexes. I can verify that because I have a LIST.INDEX printout from a few months ago showing them. However, they are no longer in place. When I run LIST.INDEX against the file, it reports there are none. I checked at the Unix level and there was still an index file (X_TX.ARCHV) next to the data file. Not knowing what else to do, I tried to add one of the indexes back to the file. I got this: CREATE.INDEX TX.ARCHV TXA.CAMPAIGN TXA.CAMPAIGN: can not create multiple indices on same location After that, the index showed up in LIST.INDEX. Furthermore, LIST.INDEX tells me the index is built, and selections on the file behave like there are built indexes in place. Anyone have any ideas as to what's going on here? Should I be concerned? The file in question is a dynamic file, if that is of any relevance. System info: UniData 6.0.11 on Tru64 Unix 5.1a. Thanks, Josh Marcus --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UD] disconnected index
Josh Marcus wrote: Has anyone ever seen a UniData file have its index become disconnected from the data file? I have a file that used to have indexes. I can verify that because I have a LIST.INDEX printout from a few months ago showing them. However, they are no longer in place. When I run LIST.INDEX against the file, it reports there are none. I checked at the Unix level and there was still an index file (X_TX.ARCHV) next to the data file. Not knowing what else to do, I tried to add one of the indexes back to the file. I got this: CREATE.INDEX TX.ARCHV TXA.CAMPAIGN TXA.CAMPAIGN: can not create multiple indices on same location After that, the index showed up in LIST.INDEX. Furthermore, LIST.INDEX tells me the index is built, and selections on the file behave like there are built indexes in place. Anyone have any ideas as to what's going on here? Should I be concerned? The file in question is a dynamic file, if that is of any relevance. System info: UniData 6.0.11 on Tru64 Unix 5.1a. The index for a dynamic UniData file is not stored as X_file. Instead, the index is stored in idx00n partitions inside the directory that holds the primary and overflow partitions. Is it possible that someone converted this file to dynamic recently and the index conversion part of the process didn't go through properly - maybe because of permissions? I've seen scenarios where over zealous system administrators imposed a 0111 umask which meant you could create a new directory for a dynamic file, but couldn't subsequently do much with it because you couldn't list its contents! Anyhow, the X_TX.ARCHV is certainly not related to any indexes on TX.ARCHV if TX.ARCHV is really a dynamic file, in which case TX.ARCHV will be a directory at the OS level. You CAN disconnect an index from a file but leave the OS index files in place, but you either have to have some file corruption, or someone playing cleverly (or stupidly) with fileview. I'd strongly recommend you check the VOC pointer for TX.ARCHV and make sure that the one you are looking at at the OS level is the same one being accessed when you are inside UniData. I'd then check if it really is a dynamic file, and if so, then simply rename your X_TX.ARCHV as something which will remind you to delete it after a day or so. Then run guide against the file to check for any corruption, fix that up with fixfile, and then re-address the indices question. If LIST.INDEX shows you that there really is an index, run guide_ndx against it and consider doing as Colin suggests and DELETE.INDEXing everything before CREATE.INDEXing them again. Cheers, Ken --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UD] disconnected index
I agree. I've seen this when a user has moved an index file around at the OS level and there is a mismatch between the number of indexes recorded in the header of the primary file and the actual number of indexes in the index file. The advise to DELETE.INDEX fn ALL, and recreate and rebuild is appropriate. Wally Terhune Manager - U2 Advanced Technical Services IBM Information Management Solutions Tel: 303.294.4866 Fax: 303.294.4832 [EMAIL PROTECTED] www.ibm.com/software/data/u2/support - Open, Query, Update, Search - Online! Alfke, Colin [EMAIL PROTECTED] To Sent by: u2-users@listserver.u2ug.org [EMAIL PROTECTED] cc stserver.u2ug.org Subject RE: [U2] [UD] disconnected index 03/14/2005 10:14 AM Please respond to u2-users I've only seen this when moving around files at the OS level. I certainly wouldn't trust this index and would delete and rebuild it. Colin Alfke Calgary, AB -Original Message- From: Josh Marcus Has anyone ever seen a UniData file have its index become disconnected from the data file? I have a file that used to have indexes. I can verify that because I have a LIST.INDEX printout from a few months ago showing them. However, they are no longer in place. When I run LIST.INDEX against the file, it reports there are none. I checked at the Unix level and there was still an index file (X_TX.ARCHV) next to the data file. Not knowing what else to do, I tried to add one of the indexes back to the file. I got this: CREATE.INDEX TX.ARCHV TXA.CAMPAIGN TXA.CAMPAIGN: can not create multiple indices on same location After that, the index showed up in LIST.INDEX. Furthermore, LIST.INDEX tells me the index is built, and selections on the file behave like there are built indexes in place. Anyone have any ideas as to what's going on here? Should I be concerned? The file in question is a dynamic file, if that is of any relevance. System info: UniData 6.0.11 on Tru64 Unix 5.1a. Thanks, Josh Marcus --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ [demime 1.01d removed an attachment of type image/gif which had a name of graycol.gif] [demime 1.01d removed an attachment of type image/gif which had a name of pic03337.gif] [demime 1.01d removed an attachment of type image/gif which had a name of ecblank.gif] --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
