That's precisely how it presented to us. If it was built on an earlier version it would update OK - but as soon as we rebuilt it just wasn't right.
Other ideas: Check the *log files in @udthome/bin. Likely udt.log, udt.errlog, not sure if 5.2 had udtsort.log? Make sure you have enough space in /tmp (@udttmp) as the index needs it. Usually you get an error though if it runs out of space. If the rebuild didn't work when everyone was off (and you made sure it was deleted at the Aix level) then you could delete the index (make sure it's gone) copy all of the records out of the file. Re-create the index, copy all of the records back in. I did notice that it looks like the index is defined as a "M" though it looks like it should be an "S". Try re-saving the dict item in SB+, make sure <6> of the UD dictionary is "S" and then delete and re-create the index - while everyone is off. Good luck Colin Alfke Calgary, AB >-----Original Message----- >From: Kevin King > >I've tried rebuilding the index both while the users are >logged on, and when the users are logged off, and the problem >persists. We've even rebooted. I've recommended to the >client they need to contact the vendor (which is their only >path to IBM) so we'll see where that gets us. What's weird is >that this worked just fine until a few days ago. I rebuilt >the index via BUILD.INDEX and trouble started. ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
